MuleSoft Accelerator for Salesforce B2C Commerce Cloud

v1.3

30 October 2020

Functional changes

• Customer sync: B2C Commerce Cloud → Service Cloud use case: Take customer profiles created or updated in B2C Commerce Cloud and push them to an external OMS.
• Customer sync: B2C Commerce Cloud→ SAP use case: Take customer profiles created or updated in B2C Commerce Cloud and push them to SAP.
• Added support for Client ID enforcement to all APIs.

Ease of use updates

• Simplified build and deployment by referencing parent POM and Common Core library as Exchange dependencies.
• Separated build and deployment scripts from parent POM into a separate resource.
• Broke monolithic build script into separate scripts for Common Services, Service Cloud, and Commerce Cloud builds.
• Migrated PDF-based setup and reference architecture guides to individual Exchange overview and asset pages.
• Separated Service Cloud vs. B2C Commerce Cloud overview pages.
• Created Postman collection to configure required Anypoint MQ resources, which can be found here.

API specification improvements

• Simplified use of multiple fragments by creating a single shared library.
• Removed unnecessary data type definitions from all definitions.
• Asset name change for consistency: Qualified all accelerator components with "Accelerator". This will also be reflected in the Exchange asset IDs, "accelerator-" for API specifications, and "accel-" for implementation templates.
• Removed displayName tags on endpoints for better clarity in Exchange.

Miscellaneous

• Upgraded Anypoint connectors and Mule modules to the latest supported versions.

Defect fixes

• SAP System API — Timezone issue fix for update polling watermark.
• SAP BAPI — modified based on issue reported by CloudGaia.

Connector names and versions

All of the templates are updated with the most current connectors, per the following:

v1.2

17 July 2020

Documentation

• Set-up guide v1.2
• Reference architecture v1.2

Change summary

The focus of release 1.2 is on increasing ease of use and enhancing developer experience.

• NEW: B2C Commerce Cloud use cases (B2C Commerce Cloud - use cases 3 & 4 in the reference architecture)
  • Order creation/capture: B2C Commerce Cloud → Order Management System (OMS): Taking orders created in B2C Commerce Cloud and pushing them to an external OMS.
    • Export schedule is set in Commerce Cloud by the administrator user.
  • Order status update: OMS → B2C Commerce Cloud: Keeping B2C Commerce Cloud updated with the status of an order, pulled from an external OMS.
    • An administrator sets the schedule for export of order status to Commerce Cloud
• UPDATED: Common component -- Notification service: Slack notification was added.
• UPDATED: All templates were updated with the most current connectors. Updates include:

v1.1

24 April 2020

Documentation

• Set-up guide v1.1
• Reference architecture v1.1

Change summary

The focus of release 1.1 is on increasing ease of use and enhancing developer experience.

• NEW: Scripts for building and deploying all Accelerator assets, in the right order, to simplify and accelerate deployment. Each script is ready to run except for configuration values - look for the string “REPLACE_BY_USER”; all such values are mandatory and must be set to legitimate values to get a useful result.
  • The parent-POM project will build all components of the Accelerator suite, automatically in the right order
  • Included: Bash and Windows scripts to build and deploy all applications with one command.
  • Included: Bash and Windows scripts with each project to deploy that project alone. Building projects individually is possible but take care to use the parent-POM to build everything if any child components (eg. core services) are changed.
• NEW: Apart from SAP proprietary JARs (which we cannot distribute), the assets in the Accelerator are self-contained; there is no need to download and install anything else. Once the SAP JARs appropriate for your platform are acquired and installed, one Maven command will build all the APIs in one step.
• UPDATED: All templates were updated with the most current connectors. Updates include:
  • Aggregators 1.0.1
  • AMQ 3.1.0
  • APIkit 1.3.9
  • DB 1.7.0
  • Email 1.1.7
  • HTTP 1.5.14
  • Mule-module-apikit-odata 2.0.2
  • Object Store 1.1.3
  • Salesforce 10.0.1* / 9.9.0
  • SAP 5.1.1
  • Secure configuration 1.2.1
  • ServiceNow 6.5.0
  • Sockets Connector 1.1.5
  • Twilio 3.0.2
  • Validation module 1.4.0
  • VM 2.0.0

*Note: Salesforce topic-listener API was not upgraded to 10.0.1

• UPDATED: Outbound connectors are all configured with retry. Retry-configuration is externalized.
• UPDATED: All configuration values for connectors are externalized as before. To enable rapid configuration, password-encryption has been removed. All passwords/secrets are configured using hidden properties for CloudHub deployments.Out-of-the-box configuration within the connector simplifies deployments to CloudHub.
• REMOVED: JSONLogger has been removed. While a helpful resource, we deemed the Accelerator can function optimally without it.

Users who want to use or are already using JSONLogger can easily do so by replacing the standard Logger with JSONLogger and configuring it as desired.

v1.0

30 January 2020

Documentation

• Set-up guide v1.0
• Reference architecture v1.0